Get Number Module - Msg On Failed Validation

[Guest miva]

hey,

 

I am using VG For Dialogic - V6.0.3335.

 

I have a "Get Numbers" module asking for a credit card number followed by the hash key. I have set the number limits to a minimum of 15 and a maximum of 16.

If the caller enters less than 15 numbers and enters the hash key, the "Message that the entered number was not correct length or failed validation" plays as it should.

However, if the caller enters more than 16 digits, the "Get Numbers" module automatically plays the "Ask caller to enter number" message.

 

Can the module be set to play the "Message that the entered number was not correct length or failed validation" on both types of fails?

 

I know I could add a "Play Message" module with that same wav file, but then I lose the ability for the caller to key ahead over the message while still maintaining the get number functionality.

 

Thank you

[SupportTeam]

If the maximum number of digits is specified in the Get Numbers module, the module will only wait for that many digits and will go down Success path (or run verification VBScript) immediately after the last digit has been entered.

 

Are you perhaps running a VBScript verification in this module as well and the verification script is not returning any results?

 

 

If you still have problems with this script please post a copy of VoiceGuide's Trace Logs which captures the problem, this will allow us to see what happened.

 

Enable logging by setting the log levels to 10 in VG.INI as per below:

[Log]

 

VoiceGuide=10

Then restart VG and make a test call which demonstrates the problem.

 

Trace files will be created in VG's \log\ subdirectory.

 

Please post the traces and the VoiceGuide script used.

 

When posting traces/scripts please .ZIP them up and post them as attachments.

[Guest miva]

I am not running any VBScripting but I feel I may have inadequately described what is occurring or at least what I would like to happen.

The Get Numbers module is working as I believe it was intended but I have an issue.

 

The "Get Numbers" module requests a credit card number followed by the hash key. I have set the number limits to a minimum of 15 and a maximum of 16.

 

If the caller enters less than 15 numbers and enters the hash key, the "Message that the entered number was not correct length or failed validation" plays as it should.

 

Say the caller accidentally entered 17 digits (for whatever reason?!) once they enter the 16th digit the "Get Numbers" confirmation message will start playing. Therefore if any additional digits are entered they will inadvertently key ahead through the confirmation module. In effect skipping this module without realising.

 

The client would like the same (failed) message played when the caller enters less digits and more digits. Is there someway we can customise the GetNumbers module? What is the simplest solution around this? A VBScript? The customer does not want to increase the maximum nunmber length as this could result in acceptance and playing back of invalid credit card numbers.

 

[SupportTeam]

If the module is asking for caller to press the hash/pound key then the best approach is to not use the maximum number length setting (or set it to large value). Just wait till the hash/pound key is pressed and then check the entered number length in the validation VBScript. From the Validation VBScript you can jump/branch to a different module which can play the same message which is played automatically by the GetNumbers module if the length is too short.

 

If you are using VBScript then you can validate the entered number not just for valid length but also calculate and confirm the entered number’s check digit(s).

[ktruk]

In my scripts, sometimes I have followed the GetNumber module with a 'dummy' play module that takes the extra digit (0-9) or hash to clear it, and proceed from here. It has a default 1 sec timeout so in practice it gets ignored if no extra digits, but wastes a second. However, with the introduction of 18 digit credit-card numbers (in the uk?) then I am going back to either hash entry for all strings, or time-outs. (I also have had problems with mobile phones where the 'send buffer' does not clear, unless you press a hash sometimes, so having long strings of number entries with hashs in helps.

[Guest miva]

Thanks for the responses Support and ktruk.

We managed to use a VBScript to get around the issue and the customer is happy with it.